Systems and methods for dynamic quality of service

ABSTRACT

Systems, methods, and apparatus for routing are provided in which a connection track comprising a plurality of network or transport layer packets, received by a router, is identified by examination of header fields of one or more first packets in the plurality of packets. One or more quality of service (QoS) parameters is associated with the connection track by determining whether the track encodes a data type by (i) an identification of a predetermined application protocol used within the one or more first packets and/or (ii) a comparison of a payload of one or more packets in the plurality of packets to known data type formats. A first QoS parameter is set to a first value in a first value range when the connection track contains the first data type. The connection track is routed through the router in accordance with the one or more QoS parameters assigned to the connection track.

CROSS REFERENCE TO RELATED APPLICATION

The present application is a continuation-in-part of U.S. patentapplication Ser. No. 11/805,407 entitled “Systems and Methods forDynamic Quality of Service,” that was filed on May 22, 2007, nowabandoned.

FIELD OF THE INVENTION

The present invention relates to systems and methods for dynamic QoSrouting where a connection track comprising data is routed from sourceto destination by a router path that satisfies the QoS (e.g., bandwidthand delay) requirements of the connection track.

BACKGROUND OF THE INVENTION

Many IP routers typically support only “best effort” traffic. However,the bandwidth available to people has been increasing rapidly with theadvent of broadband access. The result is that many new services are nowdesired that require better QoS than “best effort” IP can support. Also,with broadband, the problem of controlling the total usage and carrierexpense has become important. Thus, it has become necessary to improveboth the delay performance and the control of bandwidth for IP service,much as was accomplished in ATM. Also, call rejection for high bandwidthstreaming services like video is required instead of random discards ifquality is to be maintained.

Moreover, new quality of service (QoS) standards require that networkdevices, such as network switches, address these requirements. Forexample, the IEEE 802.1 standard divides network traffic into severalclasses of service based on sensitivity to transfer latency, andprioritizes these classes of service. The highest class of service isrecommended for network control traffic, such as switch-to-switchconfiguration messages. The remaining classes are recommended for usertraffic. The two highest user traffic classes of service are generallyreserved for streaming audio and streaming video.

If all paths within a network are fully loaded, some networks discardpackets. Discarding correctly is an important component for achievingefficient QoS for data transmissions. Internet applications tend toquickly fill all of the buffers on a conventional network. Algorithmssuch as random early discards (“RED”), which are proportional to thebuffer fill, can save the switch from becoming overloaded by suchInternet applications, but unfortunately interferes with the QoS of suchtransmissions. In one example, for TCP, a conventional network cannotavoid discarding before the user is up to the available rate. For UDP, aconventional system cannot discard even though the stream is at anacceptable rate.

Several conventional protocols have been proposed to attempt to addressexisting QoS limitations in an IP network. One exemplary protocol, theresource reservation protocol (“RSVP”), is described within the InternetEngineering Task Force (“IETF”)'s request for comments (“RFC”) for“Resource ReSerVation Protocol (RSVP)—Version 1 FunctionalSpecification” (“RFC 2205”) and “Specification of Guaranteed Quality ofService” (“RFC 2212”) was intended to allow a router flow to signal itsrequirements. However, the complexity and processing time involved withRSVP negotiation makes RSVP, by itself, unsatisfactory.

Another exemplary protocol, the differentiated Services (“DiffServ”)protocol is an alternative technique to RSVP, which utilizes sixDiffServ bits in the IP header to indicate one of several limited QoSclasses. In particular, as discussed in the IETF's “Definition of theDifferentiated Services Field (DS Field) in the IPv4 and IPv6 Headers”(“RFC 2474”) and “An Architecture for Differentiated Services” (“RFC2475”), DiffServ is intended to allow network service providers to offerto each network user a range of network services which aredifferentiated on the basis of performance. In such a scheme, by markinga specific field (e.g. the DS field) of each packet with a specificvalue, a user can request, on a packet by packet basis, a specificlimited performance class level. This value would specify the per-hopbehavior to be allotted to that packet within the provider's network.

Typically, the user and network provider would negotiate a policy (e.g.policing profile) that describes the rate at which traffic can besubmitted at each service class level. Packets submitted in excess ofthis profile would not be allotted the service class level requested. Animportant feature of DiffServ is viewed to be its scalability, whichallows the protocol to be deployed in very large networks. Thisscalability is achieved by forcing as much complexity out of the core ofthe network and into the boundary devices that process lower volumes oftraffic and lesser numbers of flows. However, this protocol hassignificant limits that preclude DiffServ from providing an effectivesolution to the problems faced with implementing QoS in an IP network.For example, DiffServ is a traffic classification technique that onlyhas six bits with a total of only thirteen general service classesdefined. Four classes are reserved for assured service. One class isreserved for expedited service. There are, however, no QoS definitionsto quantify each class, which thereby limits the QoS types that can besupported. Since the Internet will need to be able to carry a widevariety of QoS types, this quantification limitation greatly restrictsthe future use of DiffServ-based QoS in large networks. Byoversimplifying the QoS characterization problem by relying upon simplenon-quantified classes, the overall effectiveness of such QoS in IP hasbeen minimized.

DiffServ in the IP context also does not allow each packet to be routedwith state information associated with each packet. Only one route isallowed by the border gateway protocol (“BGP”) and the routingprotocols. DiffServ allows packets to be grouped by DiffServ classes androuted together as part of a composite flow. However, such compositeflows may far exceed the routing path's capacity. In addition, multipleroutes cannot be used because of packet ordering problems. With no stateinformation and only DiffServ bits, the best that a conventional switchcan do is to set up multiple queues, each receiving all of the packetsof a specific QoS class. Within such a queue, there would be no way toavoid head-of-line blocking. Since the queues do not correspond tosingle micro-flows, weighted fair queuing (“WFQ”) cannot achieve animprovement in such factors as delay variation.

The IETF has proposed an alternative conventional protocol, within RFC2702, entitled “Requirements for Traffic Engineering Over Multi ProtocolLabel Switching (“MPLS”).” MPLS utilizes a routing approach whereby thenormal mode of operation is that the operator of the network explicitlysets up MPLS composite flows on a static basis across the network. EachMPLS composite flow also is manually assigned a QoS by the operator.

MPLS provides a simple “core” set of mechanisms which can be applied inseveral ways to provide a rich functionality. Since MPLS defines anarchitecture and protocol for encapsulating IP traffic in new routingheaders, it involves a much more extensive change to conventional IPnetworks than Diffserv which is exclusively focused on existingrouting-independent IP packet fields. The MPLS approach to indicating IPQoS parameters is different from the approach defined in Diffserv. Inparticular, the MPLS label is intended to improve efficiency and controlof the switch network and allow switches to forward packets usingpredetermined paths according to, among other things, specified QoSlevels.

The disadvantage of MPLS, however, like DiffServ, is that the switch canonly identify a small set of “standard” QoS patterns, thereby greatlyrestricting the future services available to a network that requires awide variety of QoS types to be used. Furthermore, even though MPLSallows multiple composite flows on multiple routes, there still arerestrictions on multiple paths. In addition, router micro-flows stillmust be grouped into composite flows. Therefore, like DiffServ, when apath becomes overloaded, there is no way to reject new micro-flows or tosplit the composite flow into micro-flows and use alternative routes.Instead, MPLS can only drop random packets.

Another drawback with known QoS systems is that they typically requiremanual intervention to set up and maintain. This can be a difficult andtime consuming task. Given the above background, what is needed in theart are improved systems and methods for providing QoS that are moreautomated and easier to use.

SUMMARY OF INVENTION

The present invention overcomes the deficiencies in the prior art. Oneor more header fields of network layer or transport layer packets,received by a router, are examined and, based on the values found in theheader fields, assigned to connection tracks. That is, those packetsthat are communicating the same message, such as a file, video, oraudio, are assigned to the same connection track. Then, advantageously,the data type of the message carried by a connection track is determinedand QoS parameters are assigned to the connection track based upon thisdata type. The connection track is then routed through the router inaccordance with the one or more QoS parameters. This process providesthe advantage of routing connection tracks based on message data type.This leads to improved router performance. Furthermore, this leads toimproved control over the data being routed. For example, at times whenthe router is receiving too much data, the router can make intelligentdecisions on which connection tracks to route and which connectiontracks to drop. In one case, assume that the router can only route Nstreaming videos at any given time and still deliver the streaming videoto endpoints in real time. If the router is receiving M connectiontracks that each contain real-time streaming video, where M is greaterthan N, than the router can proactively drop M-N of the connectiontracks in order to deliver the N connection tracks in real time toendpoints.

One aspect of the invention provides a routing method comprisingidentifying a connection track comprising a plurality of network layeror transport layer packets, received by a router, by examination of oneor more header fields of one or more first packets in the plurality ofnetwork layer or transport layer packets. As used herein, the term“first packet” does not necessarily mean that such packets are the firstpackets to be received sequentially in time for a given connection trackby a router. The term “first packet” merely serves to identify some orall of the packets in the plurality of packets that constitute aconnection track. It will be appreciated that any subset of the packetsin the plurality of packets that constitute a connection track can serveas the one or more first packets. It will also be appreciated that allof the packets in the plurality of packets in the connection track canserve as the one or more first packets. One or more quality of service(QoS) parameters are associated with the connection track by determiningwhether the connection track encodes a first data type. Exemplarymethods by which the first data type can be determined comprise (i) anidentification of a predetermined application protocol used within theone or more first packets and/or (ii) a comparison of a payload of oneor more packets in the plurality of network layer or transport layerpackets to one or more predetermined data type formats. A first QoSparameter in the one or more QoS parameters is set to a first value in afirst value range when the connection track is determined to contain thefirst data type (e.g., the message encoded within the connection trackis a first data type such as real-time streaming video, real-timestreaming audio, etc.). Then, the connection track is routed through therouter in accordance with the one or more QoS parameters.

In some embodiments, the first QoS parameter in the one or more QoSparameters is set to a second value in a second value range when theconnection track is determined to not contain the first data type. Insome embodiments, the first QoS parameter is a queue requirement, a pathdesignation, or a router processor requirement.

In some embodiments, a second QoS parameter in the one or more QoSparameters is set to a second value in a second value range when theconnection track is determined to contain the first data type and athird QoS parameter in the one or more QoS parameters is set to a thirdvalue in a third value range when the connection track is determined tocontain the first data type. In some embodiments, the first QoSparameter is a queue requirement, the second QoS parameter is a pathdesignation, and the third QoS parameter is a router processorrequirement.

In some embodiments the first data type is video data, audio data, aphotographic image, HTML, a binary executable, real-time streamingvideo, real-time streaming audio, or video on demand. In someembodiments, the identification of a predetermined application protocolused within the one or more first packets comprises determining whetherthe one or more first packets contain real-time transport protocol (RTP)information. In some embodiments, the first data type is voice data and,when the one or more first packets contain real-time transport protocol(RTP) information, the identification of a predetermined applicationprotocol further comprises (i) determining that the connection trackencodes real-time streaming video data when the one or more first datapackets use the real-time streaming transport (RTSP) protocol (or anequivalent protocol) and (ii) determining that the connection trackencodes real-time streaming audio data when the H.323 protocol (or anequivalent protocol) is used within the one or more first packets. Asused herein, a connection track refers to those packets that encode thesame message. For example, the packets that collectively encode aparticular file, real-time streaming video source, real-time streamingaudio source, or image form a connection track.

In some embodiments, the plurality of network layer or transport layerpackets includes, but is not limited to, transmission control protocol(TCP) packets, user datagram protocol (UDP) packets, datagram congestioncontrol packets (DCCP), stream control transmission protocol (SCTP)packets, GPRS tunneling protocol (GTP) packets, or Internet ControlMessage Protocol (ICMP) packets. In some embodiments, the router is apacket router. In other embodiments, the router is a flow router.

In one aspect, the first data type is real-time streaming video and theconnection track comprises an encoded video and the associating stepfurther comprises determining a characteristic of the encoded video. Insome embodiments (i) the first QoS parameter is set to a second value inthe first value range when a value of the characteristic is withinsecond value range and (ii) the first QoS parameter is set to a thirdvalue in the first value range when a value of the characteristic iswithin a third value range. In some embodiments, the characteristic ofthe encoded video is a video code bitrate for the encoded video. In oneexample, the first QoS parameter is a queue requirement that is set tothe second value when the video code bitrate is 0.5 Mbit/second or less.In another example, the first QoS parameter is a queue requirement thatis set to the second value when the video code bitrate is 1.0Mbit/second or less. In still another example, the first QoS parameteris a queue requirement that is set to the third value when the videocode bitrate is 0.5 Mbit/second or greater. In yet another example, thefirst QoS parameter is a queue requirement that is set to the thirdvalue when the video code bitrate is 1.0 Mbit/second or greater.

In some embodiments, a wrapper (e.g., an additional header) encodes apacket in the plurality of network layer or transport layer packets andthe associating step further comprises storing the first QoS parameterin the wrapper and an external lookup table is not used. In someembodiments, each packet in the plurality of network layer or transportlayer packets is encoded with a wrapper in a plurality of wrappers, andthe associating step further comprises (i) storing the one or more QoSparameters for the connection track in a lookup table and/or (ii)storing a pointer to the one or more QoS parameters for the connectiontracks in each wrapper in the plurality of wrappers in a lookup table.In some embodiments, the lookup table comprises the QoS parameters for aplurality of connection tracks in the router. In some embodiments, themethod further comprises purging the lookup table of the QoS parametersfor a connection track in the plurality of connection tracks when therouter completes routing of the connection track.

In some embodiments, the first data type is a video format and the oneor more predetermined data type formats are one or more predeterminedvideo type formats (e.g., any of the predetermined video type formatsset forth in Table 2, below)

In some embodiments, the method further comprises (i) evaluating arouter load and (ii) either (a) dropping one or more connection tracksbased upon the first value for the first QoS parameter or (b) reducingtraffic by changing the QoS parameters of one or more connection trackswhen the router load exceeds a threshold value or some other networkcondition (e.g., network congestion) exists. The term “router load”refers to the amount of utilization of a router at a given time. Routerutilization can be measured by any combination of several metricsincluding, but not limited to, the extent to which the router processoris being used in a given period of time, current available routerbandwidth available as compared to total router bandwidth capability,router path bandwidth availability. In some embodiments, the first QoSparameter is a queue QoS requirement and the method further comprises(i) evaluating queue status and (ii) either (a) dropping one or moreconnection tracks from the router or (b) reducing traffic by changingthe QoS parameters (e.g., router queue buffer size required by aconnection track, maximum allowable delay time for a connection track, aconnection track bandwidth requirement) of one or more connection trackswhen the router queue status evaluation determines that the routercannot handle a particular connection track with its existing connectiontrack QoS parameters. For example, in some embodiments the queue QoSparameter is buffer size and, upon evaluation of router queue status,(i) one or more connection tracks are either dropped when a router hasno available queue available with sufficient buffer size and/or (ii) thebuffer size QoS parameters for one or more connection tracks isdownwardly adjusted. In another example, the connection track QoSparameter is maximum allowable delay time and, upon evaluation of routerqueue status, (i) one or more connection tracks are either dropped whenthe router cannot route the connection track within the maximumallowable delay time specified by the connection track QoS parameterand/or (ii) the maximum allowable delay time QoS parameter of one ormore connection tracks is increased. In still another example, theconnection track QoS parameter is a connection track bandwidthrequirement and, upon evaluation of router queue status, (i) one or moreconnection tracks are either dropped when the router cannot route aconnection track within the bandwidth requirements specified by theconnection track QoS parameter for the connection track and/or (ii) thebandwidth QoS parameter of each of one or more connection tracks isdecreased, and/or (iii) adjusting a maximum upload rate and/or a maximumdownload rate between the router and an Internet Service Provider. Insome embodiments, the first QoS parameter is a router processorrequirement, and the method further comprises (i) evaluating routerprocessor load and (ii) either (a) dropping one or more connectiontracks from the router and/or (b) changing QoS parameters of one or moreconnection tracks to reduce traffic through the router when insufficientrouter processor resource is available to process a connection track. Insome embodiments, the first QoS parameter is path designation, and themethod further comprises (i) evaluating router status and (ii) assigninga router path to the connection track based on the data type stored inthe connection track, router status, and optionally router policy.

In some embodiments, the determination of whether the connection trackencodes the first data type is performed by (i) the identification ofthe predetermined application protocol used within the one or more firstpackets and/or (ii) the comparison of a payload of one or more packetsin the plurality of network layer or transport layer packets to one ormore predetermined data type formats. In some embodiments, thedetermining whether the connection track encodes the first data type isfurther performed by determining a TCP or UDP port on which the routerreceived the connection track. For example, such port information canserve as a preliminary indication of connection track data type, butmore careful analysis is needed to confirm the preliminary indication(e.g., examination of application layer protocols used in the connectiontrack packets and or comparison of the payload format of the connecttrack packets to the format of know data types).

Another aspect of the invention provides a computer-readable mediumstoring computer programs executable by a computer to perform a routingmethod comprising identifying a connection track comprising a pluralityof network layer or transport layer packets, received by a router, byexamination of one or more header fields of one or more first packets(e.g., examination of one packet, examination of two packets,examination of three packets, etc. in the connection track) in theplurality of network layer or transport layer packets. One or more QoSparameters are associated with the connection track by determiningwhether the connection track encodes a first data type by (i) anidentification of a predetermined application protocol used within theone or more first packets and/or (ii) a comparison of a payload of oneor more packets in the plurality of network layer or transport layerpackets to one or more predetermined data type formats. A first QoSparameter in the one or more QoS parameters is set to a first value in afirst value range when the connection track is determined to contain thefirst data type. The connection track is routed through the router inaccordance with the one or more QoS parameters.

Another aspect of the invention provides an apparatus for routing datapackets. The apparatus comprises a processor and a memory, coupled tothe processor, the memory storing instructions for execution by theprocessor, the instructions comprising instructions for identifying aconnection track comprising a plurality of network layer or transportlayer packets, received by a router, by examination of one or moreheader fields of one or more first packets in the plurality of packets.The instructions stored by the memory further comprise instructions forassociating QoS parameters with the connection track by determiningwhether the connection track encodes a first data type by (i) anidentification of a predetermined application protocol used within theone or more first packets and/or (ii) a comparison of a payload of oneor more packets in the plurality of network layer or transport layerpackets to one or more predetermined data type formats. A first QoSparameter in the one or more QoS parameters is set to a first value in afirst value range when the connection track is determined to contain thefirst data type. The memory further comprises instructions for routingthe connection track through the router in accordance with the one ormore QoS parameters.

In some embodiments, the memory further comprises a lookup table andeach packet in the plurality of network layer or transport layer packetsis encoded with a wrapper in a plurality of wrappers. In suchembodiments, the associating step further comprises (i) storing the oneor more QoS parameters for the connection track in the lookup tableand/or (ii) storing a pointer to the one or more QoS parameters for theconnection tracks in each wrapper in the plurality of wrappers in alookup table. In some embodiments, the lookup table comprises the QoSparameters for a plurality of connection tracks in the router. In someembodiments, the memory further comprises instructions for purging thelookup table of the QoS parameters for a connection track when therouter completes routing of the connection track.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a first system that includes a router for routingdata.

FIG. 2 illustrates a process for routing data.

FIG. 3 illustrates a second system that includes a router for routingdata.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DETAILED DESCRIPTION

One or more header fields of network layer or transport layer packets,received by a router, are examined and, based on the values found in theheader fields, assigned to connection tracks. For example, in someembodiments, transmission control packets (TCP) are received and thesource port, destination port, and/or sequence number headers areexamined. TCP packets that have the same source port, destination port,and a unique sequence number are assigned to the same connection track.In this manner, those packets that are communicating the same messageare assigned to the same connection track. Then, advantageously, thedata type of the message carried by the connection track is determinedand, from this data type, QoS parameters are assigned to the connectiontrack.

In some embodiments, the first attempt to determine the data type of themessage carried by the connection track comprises attempting to identifyan application protocol used within one or more packets in theconnection track. As used herein, a connection track refers to thosepackets that encode the same message. For example, the packets thatcollectively encode a particular file, real-time streaming video,real-time streaming audio, still image or audio source form a connectiontrack. In one example, if a packet in the connection track usesreal-time transport protocol (RTP), than the packet can be furtherexamined to determine if the packet is associated with an RTP controlprotocol packet. If so, than the data type of the message contained inthe connection track is deemed to be video. On the other hand, if thepacket uses RTP, and further contains H.323, than the data type of themessage contained in the connection track is deemed to be audio becauseH.323 is predominantly used for audio applications such as voice overInternet. In another example, the HTTP protocol can carry either HTMLdata or real-time streaming video. Thus, if a packet in the connectiontrack uses the HTTP protocol, than the packet can be further examined todetermine if the packet contains HTML. If the packet does contain HTML,than the data type of the message contained in the connection track isdeemed to be HTML. On the other hand, if the packet uses a real-timestreaming video protocol, than the data type of the message contained inthe connection track is deemed to be real-time streaming video. It willbe appreciated that for some protocols, more than one packet will needto be examined in order to verify that the above-identified protocolsare present in the connection track packets.

If the attempt to determine the data type of the message containedwithin the connection track by examination of one or more packets forapplication layer protocols is not successful, than the payload of oneor more packets in the connection track is compared to one or morepredetermined data type formats. For example, the payload can becompared to the format of MPEG-4 video format to determine if themessage type is video.

Once the data type of the message contained in a connection track isdetermined (e.g., by determining one or more application protocolscontained within one or more packets and/or comparison of the payload ofone or more packets to known data types), QoS parameters are assigned tothe connection track. For example, if the connection track contains amessage having a real-time streaming video message type, QoS parametersthat will ensure that the video is streamed to an endpoint at a ratethat will prevent noticeable interruption of the video are assigned tothe connection track. If the message type is real-time streaming audio,QoS parameters that will ensure that the audio is streamed to anendpoint at a rate that will prevent interruption of the audio areassigned to the connection track. Other exemplary message types that areassigned unique QoS parameters include, but are not limited to,non-streaming video, non-streaming audio, web pages, FTP transmissions,and HTML.

Once the data type of the message contained in a connection track isdetermined, the message track is routed through the router in accordancewith the one or more QoS parameters assigned to the connection track.This process provides the advantage of routing connection tracks basedon data type. Moreover, the QoS parameters assigned to a connectiontrack can optionally be used in conjunction with QoS parameters imposedby an Internet Service Provider or other QoS parameters (e.g., the IEEE802.1 standard). The inventive process leads to improved routerperformance. At times when the router is receiving too much data, theinventive process allows the router to make intelligent decisions aboutwhich connection tracks to route and which connection tracks to drop.For example, assume that the router can only route N streaming videos atany given time and still deliver the streaming video to endpoints inreal time. If the router is receiving M connection tracks that eachcontain streaming video, where M is greater than N, than the router canproactively drop M-N of the connection tracks in order to deliver the Nconnection tracks in real time.

FIG. 1 details an exemplary system that supports the functionalitydescribed above. In particular, FIG. 1 illustrates a network 100 inwhich a network switch 16 of router 102 connects start points 104A withendpoints 104B. Each of devices 104 can be any network device, such as acomputer, a printer, another network switch, or the like. Switch 16transfers (routes) data, such as connection tracks, between devices 104over channels 106A and 106B, and can also handle an arbitrary number ofdevices in addition to the devices 104 depicted in FIG. 1. Channels 106can include fiber optic links, wireline links, wireless links, and thelike. In some embodiments, router 102 is a packet router. In someembodiments, router 102 is a flow router.

An exemplary router 102 comprises:

-   -   a central processing unit or other form of microcontroller 14;    -   a system memory 30, for storing system control programs, data,        and application programs; system memory 30 may also include        read-only memory (ROM) or other forms of computer readable media        such as a hard disk drive;    -   switch circuitry 16 for routing packets and/or flows;    -   an internal bus 18 or other electronic communication system for        interconnecting the aforementioned elements; and    -   a power source 12 to power the aforementioned elements.

As illustrated in FIG. 1, memory 30 includes a connection track controlmodule 32 for assigning QoS parameters to a connection track based onthe data type of the message contained within the connection track. Insome embodiments, connection track control module 32 includesinstructions for performing any of the methods disclosed herein. Memory30 further includes a lookup table 34 that can be used to store the QoSparameters 42 of each of the connection tracks 38 that the router 102 isrouting at any given time. Lookup table 34 can optionally further storethe message data type 40 of each of the connection tracks 38 that therouter 102 is routing at any given time. Each of the data structures inmemory 30, including lookup table 34 and each of the connection trackdata structures 38 can comprise any form of stored data including, butnot limited to, flat ASCII or binary files, a relational database (SQL),or an on-line analytical processing (OLAP) database (MDX and/or variantsthereof). Furthermore, such data structures can be stored in router 102and/or in a device that is in electronic communication with router 102over a wide area network such as the Internet, or a local network.

FIG. 3 shows a network 300 that is identical to that of network 100 ofFIG. 1 with the exception that more details are given for the connectionbetween router 102 and start points 104A in accordance with a particularexemplary embodiment. In the particular exemplary embodiment illustratedin FIG. 3, data from start points 104A is provided to router 102 throughInternet Service Provider (ISP) 302. Internet Service Provider 302includes one or more network switches 304 that routes electronicinformation (e.g., data packets) from start points 104A to router 102across line 306. Router 102 then routes the packets to end points 104B.Of course, end points 104B can communicate electronic information tostart points 104A through the reverse path. In typical embodiments, line306 is characterized by an access speed that is set by ISP 302. Forexample, ISP 302 may set a download speed (data flowing to router 102)and a different upload speed (data flowing to ISP 302 from router 102).For example, the download speed may be set at 56 kbits/sec, 64kbits/sec, 256 kbits/sec, 1.5 Mbits/sec, 5 Mbits/sec, 6 Mbits/sec, 7Mbits/sec or higher. Upload speed may be set dependently orindependently of download speed at 56 kbits/sec, 64 kbits/sec, 256kbits/sec, 1.5 Mbits/sec, 5 Mbits/sec or higher. Other upload anddownload speeds are possible as well.

Now that a router 102 in accordance with various embodiments of thepresent invention have been disclosed in conjunction with FIGS. 1 and 3,an exemplary method for routing will be disclosed in conjunction withFIG. 2.

Step 202. In step 202, one or more network layer or transport layerpackets are received. Examples of network layer (also known as theInternet layer) packets include, but are not limited to Internet groupmanagement protocol (IGMP) packets, Internet control message protocol(ICMP) packets, Resource ReSerVation Protocol (RSVP) packets, IPsecurity (IPsec) packets, address resolution protocol (ARP) packets, andreverse address resolution protocol (RARP) packets. Examples oftransport layer packets include, but are not limited to, transmissioncontrol protocol (TCP) packets, user datagram protocol (UDP) packets,datagram congestion control packets (DCCP), stream control transmissionprotocol (SCTP) packets, and GPRS tunneling protocol (GTP) packets. Itwill be appreciated that transport layer packets will necessarilyinclude an underling network layer protocol (e.g., TCP/IP). As used,herein, a packet is referred to as a network layer packet when theheader of the network protocol within the packet is examined for thepurpose of assigning the packet to a connection track even though thepacket may include other protocols such as a transport layer protocol.As used herein, a packet is referred to as a transport layer packet whenthe header of the transport layer protocol within the packet is examinedfor the purpose of assigning the packet to a connection track eventhough the packet may include other protocols such as a network layerprotocol. Moreover, in some instances, the header of both a networklayer and a transport layer protocol encoded in a packet are examinedfor the purposes of assigning the packet to a connection track. In suchinstances, the packet may be referred to as a network layer packet or atransport layer packet.

Step 204. In step 204, one or more network layer or transport layerpackets received by a router are associated with a first connectiontrack 38 in a plurality of connection tracks based on values in one ormore header fields of the respective network layer or transport layerpackets. For example, in some embodiments, transmission control packets(TCP) are received and the source port, destination port, and sequencenumber header TCP headers are examined. TCP packets that have the samesource port, destination port, and a unique sequence number are assignedto the same connection track. It will be appreciated that at any giventime, router 102 will receive data packets for more than one connectiontrack. In such instances, step 204 assigns packets to differentconnection tracks 38 so that each connection track 38 comprises packetsthat encode the same message. For example, a first set of packetsreceived by the router 102 that contain a first message will bedesignated as a first connection track 38 whereas a second set ofpackets received by the router that contain a second message will bedesignated as a second connection track 38.

Steps 206-210. In step 206, one or more of the network layer ortransport layer packets assigned to a particular connection track 38 areencoded with a wrapper. The wrapper identifies the packets as belongingto the particular connection track 38. In step 208, a data structure isadded to lookup table 34 for the first connection track. In typicalembodiments, the data structure added in step 208 uniquely representsthe particular data structure. Thus, the data structure is given thesame reference 38 as the particular connection track 38 that itrepresents. For example, referring to FIG. 1, connection track 38-1 inlookup table 34 represents connection track 38-1, connection track 38-2represents connection track 38-2, and so forth. In step 210, a pointerto the data structure in the lookup table that represents the particularconnection track is placed in the wrapper of each of the one or more ofthe network layer or transport layer packets assigned to the particularconnection track. In this way, the identity of the connection track thatincoming packets belong to is stored in an efficient manner in the datapackets that make up the connection track.

Step 212. In step 212, a determination is made as to whether the packetsin a given connection track include a predetermined application layerprotocol. A predetermined application layer protocol is one in which thedata type of the connection track can be conclusively determined fromthe identity of the application layer protocol itself. The applicationlayer is the seventh level of the seven-layer open systemsinterconnection basic reference model (OSI reference model or OSI modelfor short). It interfaces directly to and performs common applicationservices for the application processes. It also issues requests to thepresentation layer. The OSI model is a layered, abstract description forcommunications and computer network protocol design, developed as partof open systems interconnection (OSI) initiative. It is also called theOSI seven layer model and is described in ISO 7498 and its variousaddenda.

Advantageously, not all of the packets in the connection track need tobe examined in step 212. In some embodiments, only a single packet inthe connection track is examined for the purpose of identifying anapplication protocol. Examples of application protocols include, but arenot limited to, dynamic host configuration protocol (DHCP), domain namesystem (DNS) protocol, file transfer protocol (FTP), gopher,multipurpose Internet mail extension protocol, post office protocolversion 3 (POP3) protocol, session initiation protocol (SIP) protocol,simple mail transfer protocol (SMTP), simple network management protocol(SNMP), secure shell (SSH) protocol, teletype network (TELNET) protocol,border gateway protocol (BGP), remote procedure call (RPC) protocol,real-time transport protocol (or RTP), transport layer security (TLS)protocol, secure sockets layer (SSL) protocol, session descriptionprotocol (SDP, RFC 4566), and simple object access protocol (SOAP,service oriented architecture protocol). If the packets contain apredetermined protocol (212-Yes), process control passes to step 216,otherwise (212-No), process control passes to step 214.

In some embodiments, the identification of a predetermined applicationprotocol (212-Yes) comprises determining whether one or more packets inthe connection track contains real-time transport protocol (RTP)information. In some embodiments, one or more packets contain real-timetransport protocol (RTP) information and the identification of apredetermined application protocol (212-Yes) further comprises (i)determining that the connection track encodes video data when the one ormore packet use the real-time streaming transport (RTSP) protocol and(ii) determining that the connection track encodes voice data when theH.323 protocol is used within the one or more packets.

In some embodiments, the TCP or UDP port number on which the routerreceived the connection track is used in conjunction with theidentification of any of the aforementioned protocol types to determinethe data type of the message encoded in the connection track. Asillustrated in Table 1 below, much information about the protocol used,and therefore data type of the message encoded in the connection track,can be determined by the identity of the port used to transmit theconnection track to the router.

TABLE 1 Services typically associated with particular TCP and UDP portsService TCP UDP Notes SSH 22 Secure Shell HTTP 80 HyperText TransferProtocol* (e.g. for web browsing). Currently (2003-07-05) HTTP/1.1 isofficially described in RFC 2616. HOSTS2 Name 81 81 Server XFER Utility82 82 RPC Endpoint 135 135 registered as “epmap - DCE endpoint Mapperresolution”. Used by Microsoft for RPC locator service. LDAP 389 389Lightweight Directory Access Protocol* MS NetMeeting LDAP or ULP, dyn >=Videoconferencing dyn >= 1024, 1024 1503, H.323 HostCall, MS ICCPTimbuktu 407, 1417-1420 407 remote control SLP 427 427 Service LocationProtocol; Used by MacOS and NetWare. HTTPs 443 secure HTTP (SSL)LPD/printer 515 515 Printing; LPD stands for Line Printer Daemon. ULP522 522 User Location Protocol (Microsoft) AppleTalk Filing 548 548Protocol (AFP) QuickTime 4 RTSP RTP-QT4 streaming audio, video RTSP 554Real Time Streaming Protocol. Currently (2003-07-05) described in RFC2326. NNTPs 563 secure NNTP news (SSL) Internet Printing 631 631 printremotely to any IPP enabled printer Protocol (IPP) through the Internet;The Common Unix Printing System (CUPS) is based on IPP. Also seeprinting section. LDAPs 636 636 secure LDAP; (LDAP protocol overTLS/SSL) Doom 666 666 network game Remotely Possible 799 remote control.CA ControlIT support. (ControlIT) VMware Virtual 902 remote control andviewing of virtual Machine Console machines. vmware-authd. SOCKS 1080internet proxy; Also used by Trojans. OpenVPN 1194 1194 * Kazaa 12141214 peer-to-peer file sharing WASTE 1337 1337 peer-to-peer. Also seeInfoAnarchy WASTE FAQ. This port is officially registered for Men andMice DNS (QuickDNS Remote). Lotus Notes Domino 1352 VocalTec Internet1490, 6670, 22555 videoconferencing Phone 25793 Citrix ICA 1494, dyn >=1604, dyn >= remote application access 1023 1023 Virtual Places 1533conferencing, also see VP voice Xing StreamWorks 1558 streaming videoNovell GroupWise 1677 1677 group collaboration; NOTE: Other (RemoteClient) features of GroupWise use many other ports. H.323 Host Call 17201720 H.323 host call PPTP 1723 virtual private network (VPN) MS ICCP1731 1731 audio call control (Microsoft) MS NetShow 1755 1755, dyn >=streaming video 1024 <= 5000 MSN Messenger 1863 instant messagingNetopia netOctopus 1917, 1921 1917 network management Big Brother 19841984 network monitoring ICU II 2000-2003 videoconferencing iSpQ2000-2003 videoconferencing glimpseserver 2001 search engineDistributed.Net 2064 distributed computation RC5/DES SoulSeek 2234, 55342234, file sharing 5534 Microsoft DirectX 2300-2400, 2300-2400 networkedmultiplayer games gaming (DirectPlay) 47624 7 Microsoft DirectX2302-2400, networked multiplayer games; only 6073 gaming (DirectPlay)6073 is registered as DirectPlay8 8 MADCAP - 2535 2535 defined in RFC2730 - Multicast Address Multicast Address Dynamic Client AllocationProtocol Dynamic Client (MADCAP); Also used by Trojans. AllocationProtocol Netrek 2592 network game ShareDirect 2705 2705 peer-to-peer(P2P) filesharing. Officially registered for Sun SDS AdministrationURBISNET 2745 2745 . Borland Interbase 3050 3050 gds_db; See CERTAdvisory CA-2001- database 01 for potential security risk. squid 31283130 web proxy cache; also used by Trojans. iSNS 3205 3205 InternetStorage Name Service iSCSI default port 3260 3260 SCSI over IP WindowsRemote 3389 registered as ms-wbt-server. RDP 5.1 is Desktop Protocol thecurrent version; Remote Desktop (RDP) Web Connection also uses HTTP.NetworkLens SSL 3410 3410 Event Virtual Places Voice 3450, 8000-9000voice chat Chat Apple iTunes music 3689 3689 Digital Audio AccessProtocol sharing (DAAP) World of Warcraft 3724 online game Mirabilis ICQdyn >= 1024 4000 locator, chat Blizzard/Battle.net 4000, 6112-6119 4000,network gaming - support (captured 6112-6119 2001-11-11), proxy andfirewall info Abacast 4000-4100, peer-to-peer audio and video streaming.4500, 9000-9100 GlobalChat client, 4020 4020 chat rooms, used to becalled ichat server PGPfone 4747 secure phone PlayLink 4747, 4748, 6144online games 10090 radmin 4899 4899 remote control Yahoo Messenger -5000-5001 5000-5010 voice chat Voice Chat GnomeMeeting H.323 5000-5003,audio and videoconference. 5000-5003 is HostCall, 5010-5013 RTP and RTCPrange for this app. 30000-30010 Yahoo Messenger - 5050 Messaging; Itwill try ports 5050, 80, any messages port. SIP 5060 5060 SessionInitiation Protocol; For audio and video. Currently (2003-07-05) seeRFCs 3261, 3262, 3263, 3264, 3265 Apple iChat AV SIP, RTP- audio andvideo conferencing; may also iChatAV need iChat local port. YahooMessenger - 5100 video Webcams AOL Instant 5190 5190 America OnLine;Also used by Apple Messenger (AIM) iChat (in AIM compatibility mode).AIM Video IM 1024-5000 ? 1024-5000 ? video chat AOL ICQ 5190, dyn >=messaging 1024 AOL 5190-5193 5190-5193 America OnLine XMPP/Jabber 5222,5269 5222, Extensible Messaging and Presence 5269 Protocol; Defined byXMPP specs (RFCs now issued), specs created by IETF group. Qnext5235-5237 5235-5237 audio/video conference, fileshare, everything. Port5236 is officially assigned to “padl2sim”. iChat local traffic 5298 5298Multicast DNS 5353 5353 Mac OS X 10.2: About Multicast DNS. Related toZeroconf which Apple has implemented as Rendezvous. (Note: the regularDomain Name Service port is 53.) Dialpad.com 5354, 7175, dyn >=telephony 8680-8890, 1024 9000, 9450-9460 HotLine 5500-5503 peer-to-peerfilesharing. SGI ESP HTTP 5554 5554 SGI Embedded Support Partner (ESP)web server; Also used by Trojans, see SGI Security Advisory20040501-01-I. InfoSeek Personal 5555 5555 This port is commonly used byHP Agent OpenView Storage Data Protector (formerly HP OmniBack).pcAnywhere 5631 5632 remote control eShare Chat Server 5760 eShare WebTour 5761 eShare Admin 5764 Server VNC 5800+, 5900+ remote controlBlizzard Battle.net 6112 6112 online gaming GNUtella 6346, 6347 6346,peer-to-peer file sharing 6347 Netscape Conference H.323 2327audioconferencing HostCall, 6498, 6502 Danware NetOp 6502 6502 remotecontrol Remote Control common IRC 6665-6669 Internet Relay ChatNet2Phone selected 6801, telephony CommCenter selected BitTorrent6881-6889, distributed data download, newer 6969 versions TCP 6881-6999;Alternate FAQ link. Blizzard World of downloads patches for World ofDownloader Warcraft, Warcraft Battle.net and BitTorrent RTP-QT46970-6999 Real-time Transport Protocol; These ports are specifically forthe Apple QT4 version. VDOLive 7000 user- streaming video specified RealAudio & Video RTSP, 7070 6970-7170 streaming audio and video CU-SeeMe,7648, 7649, 7648-7652, videoconferencing Enhanced CUSM LDAP 24032 commonHTTP 8000, 8001, 8080 Apache JServ 8007 8007 (default port) Protocol v12(ajp12) Apache JServ 8009 8009 (default port) e.g. Apache mod_jkProtocol v13 (ajp13) Tomcat connector using ajp13. See Workers HowTo forconfig info. Grouper 8038 8038 peer-to-peer (P2P) filesharing PDLdatastream 9100 9100 Printing' PDL is Page Description Language. Usedcommonly by HP printers and by Apple. MonkeyCom 9898 9898 video-chat,also used by Trojans iVisit 9943, videoconferencing 9945, 56768 ThePalace 9992-9997 9992-9997 chat environment common Palace 9998 chatenvironment NDMP 10000 10000 Network Data Management Protocol; Used forstorage backup. Also used by Trojans. Amanda 10080 10080 backupsoftware; Also used by Trojans. Yahoo Games 11999 network games Italk12345 12345 network chat supporting multiple access methods; appearsmostly used in Japan. There are many other applications callingthemselves “italk”. TrendMicro OfficeScan antivirus also uses this port.Commonly used by Trojans. RTP-iChatAV 16384-16403 Used by Apple iChatAV. RTP 16384-32767 Real-time Transport Protocol; RTP in general isdescribed in RFC 3550. Palm Computing 14237 14238 data synchronizationNetwork Hotsync Liquid Audio 18888 streaming audio FreeTel 21300-21303audioconferencing VocalTec Internet 22555 22555 audio & documentconferencing Conference Quake 26000 26000 network game MSN Gaming Zone28800-29100 28800-29100 network gaming (zone.com, zone.msn.com), alsosee DirectPlay 7 and DirectPlay 8 Sygate Manager 39213

Steps 214, 218. Step 214 is reached when the packets examined in step212 did not contain a protocol that conclusively identified the datatype of the message contained by the connection track 38. In suchinstances, the payload from one or more packets in the connection trackis extracted (step 214) and the file structure of the payload iscompared to the file structure of known data types (step 218). In someembodiments, the payload from only a single packet is extracted andcompared to the file structure of known data types. In some embodiments,the payload from two or more packets of a single connection track 38 areextracted and compared to known file types. In some embodiments, thefile format of the one or more data packets is compared to any of thefile formats listed in Table 2.

TABLE 2 Nonlimiting exemplary video file formats Extension File format.3g2, .3gp, 3GPP Multimedia File .3gp2, .3gpp .3mm 3D Movie Maker Movie.60d, .ajp CCTV Video Clip .asf Advanced Systems Format File .asxMicrosoft ASF Redirector File .avi Audio Video Interleave File .avsApplication Visualization System Format .bik BINK Video File .bix, .boxKodicom Video .byu Brigham Young University Movie .cvc cVideo .dceDriveCam Video .dif Digital Interface Format .dir Macromedia DirectorMovie .divx DivX-Encoded Movie .dv Digital Video File .dvr-ms MicrosoftDigital Video Recording .dxr Protected Macromedia Director Movie .eyeEyemail Video Recording .fla Macromedia Flash Animation .flc FLICAnimation .fli FLIC Animation .flv Flash Video .flx FLIC Animation .gl,.grasp GRASP Animation .gvi Google Video File .gvp Google Video Pointer.ifo DVD-Video Disc Information .imovieproject iMovie Project .ivf IndeoVideo Format File .ivs Internet Streaming Video .izz Isadora Patch .lsfStreaming Media Format .lsx Streaming Media Shortcut .m1v MPEG-1 VideoFile .m2v MPEG-2 Video .m4e MPEG-4 Video File .m4u MPEG-4 Playlist .m4viTunes Video File .mjp MJPEG Video File .mkv Matroska Audio/Video File.moov, .mov Apple QuickTime Movie .movie QuickTime Movie .mp4 MPEG-4Video File .mpe MPEG Movie File .mpeg, .mpg MPEG Video File .mpv2 MPEG-2Video Stream .msh Visual Communicator Project File .mswmm Windows MovieMaker Project .mvb Multimedia Viewer Book Source File .mvc MovieCollector Catalog .nvc NeroVision Express Project .ogm Ogg Vorbis VideoFile .omf Open Media Framework .prproj Premiere Pro Project .prx WindowsMedia Profile .qt Apple QuickTime Movie .qtch QuickTime Cache File .rmReal Media File .rmvb RealVideo Variable Bit Rate .rp RealPix Clip .rtsRealPlayer Streaming Media .rts QuickTime Real-Time Streaming Format.scm ScreenCam Recording .smil Synchronized Multimedia IntegrationLanguage .smv VideoLink Mail Video .spl FutureSplash Animation .ssmStandard Streaming Metafile .svi Samsung Video File .swf MacromediaFlash Movie .tivo TiVo Video File .vdo VDOLive Media File .vfw Video forWindows .vid QuickTime Video .viewlet Qarbon Viewlet .viv VivoActiveVideo File .vivo VivoActive Video File .vob DVD Video Object .vro DVDVideo Recording Format .wm Windows Media .wmd Windows Media DownloadPackage .wmv Windows Media Video File .wmx Windows Media Redirector .wvxWindows Media Video Redirector

In some embodiments the HTTP, FTP, or HTTPS protocol is identified inthe examined packets and the payload of one or more packets in theconnection track are examined to determine if the message encoded in theconnection track is video on demand by comparing the file structure ofthe payload of the one or more packets to the file structure ofpredetermined video on demand formats. In some embodiments, the RTSP,MMS, RTP unicast, RTP multicast, HTTP, or UDP protocol is identified inthe examined packets and the payload of one or more packets in theconnection track are examined to determine if the message encoded in theconnection track is real-time streaming video by comparing the filestructure of the payload of the one or more packets to the filestructure of predetermined real-time streaming video formats.

Step 216. Step 216 is reached when the data type encoded in the packetsinspected in step 212 includes a predetermined application protocol. Inone example, the predetermined protocol is a multimedia streamingprotocol such as real-time streaming protocol (RTSP), real-timetransport control (RTP), real-time transport control (RTCP), ormultimedia messaging service (MMS) and when such a protocol is found inthe connection track packets, the data type of the message containedwithin the connection track is deemed to be real-time streaming video.In some embodiments, the packets must contain RTSP or MMS in order forthe data type of the message contained within the connection track to bedeemed real-time streaming video. In some embodiments, when the packetsinclude the RTP and H.323 protocols, the connection track is deemed tobe voice.

Steps 212, 214, 216, and 218 serve to identify a data type of themessage encoded in a connection track. One of skill in the art willappreciate that there are many possible variants to steps 212, 214, 216,and 218. For instance, it is possible in some embodiments to alwayscompare the payload of one or more packets in the connection track toknow data types and never examine packet headers for the presence ofpredetermined application layer protocols. Further, in some embodiments,it is possible to always look at packet headers for the presence ofpredetermined application layer protocols as well as to always comparethe payload of one or more data packets in the connection track to knowndata formats. Furthermore, any method for conclusively determining thedata type of the message encoded within the connection track is withinthe scope of the present application, including methods that do notinvolve determining the presence of a predetermined application protocolin the header of one or more packets in the connection track orexamination of the packet payload of one or more packets in theconnection track.

Step 220. By the time step 220 is reached, the data type of the messagein the connection track is known. In step 220, QoS parameters areassigned to the connection track based upon this data type. Exemplarydata types include, but are not limited to, real-time streaming video,video on demand, audio data, a photographic image, an executable binaryprogram, and HTML. Exemplary QoS parameters that can be set for aconnection track include, but are not limited to, any combination ofqueue requirement, path designation, and router processor requirements.

The queue requirement QoS parameter refers to any of one or more queuerelated QoS parameters including, but not limited to, buffer sizerequired by the connection track, maximum allowable delay tolerated bythe connection track and/or the bandwidth requirements of the connectiontrack. For example, more intensive connection track message data typessuch as real-time streaming video require higher bandwidths. As anadditional example, connection tracks message data types such asreal-time streaming audio require reduce allowable delay.

The path designation QoS parameter refers to the router path that shouldbe used by a connection track. A slow router path is used for non-timingcritical connection track data types such as FTP downloads. A fastrouter path is used for either timing critical connection track messagetypes such as real-time streaming video, real-time audio, and/orconnection tracks that contain a large amount of data. In someembodiments, the path designation QoS parameter is assigned a value in avalue range, where one end of the value range indicates a fast routerpath (e.g., bypass the router processor or use a hardware-specified fastrouter path) and the other end of the value range indicates a slowrouter path (e.g., do not bypass the router processor and do not use ahardware-specified fast router path). Thus, for example, in someembodiments, the path designation QoS parameter is a number in the rangebetween 1 and 4 includes, where 1 indicates the slowest router path and4 indicates the fastest router path. In such embodiments, a connectiontrack that encodes a message whose data type is real-time streamingvideo could be assigned a path designation QoS parameter of “4” whereasa connection track that encodes a message whose data is an executablebinary could be assigned a path designation QoS parameter of “1”.

The router processor requirement QoS parameter provides an indication ofthe amount of router processor power that will be required to route theconnection track 38. The router processor requirement QoS parameter isadvantageous because it can be used by connection track control module32 to determine whether the router can handle the connection track. Forexample, if the router processor 14 is already fully utilized processingother connection tracks, than module 32 can make the decision tocompletely drop a new connection track with computationally intensiverouter processor requirements.

The queue requirement, path designation, and router processorrequirement QoS parameters are merely exemplary parameters that can beconstructed for a given connection track 38. In some embodiments, thedata type of the message encoded in the connection track is also storedin the data structure 38 created for the connection track (e.g., element40 of FIG. 1). In some embodiments, the data type of the message encodedin the connection track is not stored in the data structure 38 createdfor the connection track (e.g., element 40 of FIG. 1) because suchinformation is redundant to the values of the QoS parameters assigned tothe connection track in such embodiments.

Advantageously, QoS parameters can be set for connection tracks withoutintensive manual intervention. The values of such QoS parameters aredetermined by the application layer data type of the message encoded inthe packets of the connection track. Accordingly, in one embodiment, afirst QoS parameter in the one or more QoS parameters associated with afirst connection track is set to a first value in a first value rangewhen the message encoded within the connection track is of first datatype. The first QoS parameter is set to a second value in a second valuerange when the message encoded within the connection track is determinedto not be of the first data type. In some embodiments, a second QoSparameter in the one or more QoS parameters associated with the firstconnection track is set to a second value in a second value range whenthe message encoded within the connection track is determined to be thefirst data type. Moreover, a third QoS parameter in the one or more QoSparameters associated with the connection track is set to a third valuein a third value range when the message encoded in the first connectiontrack is determined to contain the first data type. In some embodiments,the first QoS parameter is a queue requirement, the second QoS parameteris a path designation, and the third QoS parameter is a router processorrequirement. In some embodiments, the first data type is real-timestreaming video, video on demand, audio data, a photographic image, anexecutable binary program, or HTML. In some embodiments, the first QoSparameter is a queue requirement, a path designation, or a routerprocessor requirement.

In some embodiments, the data type of the message is real-time streamingvideo or real-time streaming audio and further characterization of themessage is sought in order to assign QoS parameters to the connectiontrack that encodes the message. For instance, if the message is videothat has a very low bitrate, than QoS parameters appropriate for the lowresolution video are assigned to the connection track that encodes thevideo. On the other hand, if the message is a video that has a very highbitrate, than QoS parameters appropriate for the high resolution videoare assigned to the connection track. In another example, if the messageis video that delivers a low number of frames per second, than QoSparameters appropriate for such video are assigned to the connectiontrack that encodes the video. On the other hand, if the message is avideo that has a very high number of frames per second, than differentQoS parameters appropriate for such video are assigned to the connectiontrack.

In some embodiments, a first QoS parameter associated with a connectiontrack is set to a second value in a first value range when a value ofthe characteristic is within second value range and the first QoSparameter is set to a third value in the first value range when a valueof the characteristic is within a third value range. For example, insome embodiments, the data type is real-time streaming video, thecharacteristic of the encoded video is a video code bitrate for theencoded video, and the first QoS parameter is a queue requirement, wherethe queue requirement is set to the second value when the video codebitrate is 0.5 Mbit/second or less. In another example, the data type isreal-time streaming video, the characteristic of the encoded video is avideo code bitrate for the encoded video, and the first QoS parameter isa queue requirement, where the queue requirement is set to the secondvalue when the video code bitrate is 1.0 Mbit/second or less. In stillanother example, the data type is real-time streaming video, thecharacteristic of the encoded video is a video code bitrate for theencoded video, and the first QoS parameter is a queue requirement, wherethe queue requirement is set to the third value when the video codebitrate is 0.5 Mbit/second or greater. In still another example, thedata type is real-time streaming video, the characteristic of theencoded video is a video code bitrate for the encoded video, and thefirst QoS parameter is a queue requirement, where the queue requirementis set to the third value when the video code bitrate is 1.0 Mbit/secondor greater.

Step 222. In step 222, the one or more QoS parameters assigned to theconnection track are stored in a data structure 38 constructed for theconnection track in lookup table 34. Optionally the data type of themessage encoded within the connection track is stored in the datastructure as data type 40.

Step 224. In step 224, the connection track is routed through the routerby connection track control module 32 in accordance with the QoSparameters 42 of the connection track stored in the lookup table 34.Optionally, the connection track is routed in accordance with the QoSparameters 42 as well as QoS parameters imposed by an Internet ServiceProvider policy or some other user configurable router QoS policy.

In some embodiments, router 102 monitors the amount of data beingdownloaded as well as the amount of data being uploaded over line 306.When data is being downloaded to router 102 at a speed that approachesthe maximum download speed set by ISP 302, router 102 sends a request toISP 302 to temporarily increase the maximum download speed set by ISP302. For example, in some embodiments when data is being downloaded torouter 102 at speeds that approach 65 percent, 70 percent, 75 percent,80 percent, 85 percent, or 90 percent of the maximum download speed,router 102 will send a request to ISP 302 to increase the downloadspeed. In one user case scenario, consider the case where the maximumdownload speed set by ISP 302 for router 102 is 1.5 Mbits/sec and thatdata is being downloaded to the router at 1.3 Mbits/sec. Since the rateof 1.3 Mbits/sec approaches the maximum rate set by ISP 302, router 102sends a request to ISP 302 to temporarily increase the maximum downloadspeed for line 306 to 3 Mbits/sec. Router 102 continues to monitordownload rates and can make additional requests to ISP 302 to increasethe maximum download speed as needed. Moreover, when router 102 is nolonger receiving data at rates that approach the maximum download speedset by ISP 302, router 102 can make a request to ISP 302 to restore themaximum download speed to router 102 to the default speed. Thisprocedure is advantageous because it is performed without the need forintervention from an end-point 104B user or the router 102administrator.

In some embodiments, ISP 302 rather than router 102 monitors the amountof data being sent to router 102 over line 306 and automaticallyincreases the maximum download speed to router 102 when the amount ofdata being sent approaches the maximum download speed permitted by thedefault ISP policy for line 306. In some embodiments, this increase isonly performed after receiving permission from router 102. ISP 302continues to monitor traffic rates after an increase and resets thedownload speed to the default speed once the amount of data beingdownloaded no longer approaches or exceeds the default speed.

In some embodiments, router 102 monitors the amount of data beinguploaded as well as the amount of data being uploaded over line 306.When data is being uploaded to ISP 302 at a speed that approaches themaximum upload speed set by ISP 302, router 102 sends a request to ISP302 to temporarily increase the maximum upload speed set by ISP 302. Forexample, in some embodiments when data is being uploaded to ISP 302 fromrouter 102 at speeds that approach 65 percent, 70 percent, 75 percent,80 percent, 85 percent, or 90 percent of the maximum upload speed,router 102 will send a request to ISP 302 to increase the upload speed.In one user case scenario, consider the case where the maximum uploadspeed set by ISP 302 for router 102 is 1.5 Mbits/sec and that data isbeing uploaded to the ISP 302 from the router 102 at 1.3 Mbits/sec.Since the rate of 1.3 Mbits/sec approaches the maximum rate set by ISP302, router 102 sends a request to ISP 302 to temporarily increase themaximum upload speed for line 306 to 3 Mbits/sec. Router 102 continuesto monitor upload rates and can make additional requests to ISP 302 toincrease the maximum upload speed as needed. Moreover, when router 102is no longer sending data to ISP 302 at rates that approach the maximumupload speed set by ISP 302, router 102 can make a request to ISP 304 torestore the maximum upload speed to router 102 to the default speed.This procedure is advantageous because it is performed without the needfor intervention from an end-point 104B user or the router 102administrator.

In some embodiments, ISP 302 rather than router 102 monitors the amountof data being sent to ISP 302 over line 306 and automatically increasesthe maximum upload speed to ISP 302 when the amount of data being sentto ISP 302 approaches the maximum upload speed permitted by the defaultISP policy for line 306. In some embodiments, this increase is onlyperformed after receiving permission from router 102. ISP 302 continuesto monitor traffic rates after an increase and resets the upload speedto the default speed once the amount of data being uploaded no longerapproaches or exceeds the default speed.

It will be appreciated that upload speeds and download speeds have beendescribed as separate embodiments. In fact, in typical embodiments, bothupload and download speeds are monitored by router 102 and/or ISP 302and the maximum rates for upload and download speeds are adjusted whenneeded in the manner described above.

In some embodiments, step 224 comprises evaluating router 102 load andperforming the step of (i) dropping one or more connection tracks 38based upon a respective value of a QoS parameter 42 associated with eachof the one or more connection tracks 38 when the router load exceeds athreshold value and/or (ii) changing the value of each of the QoSparameters thereby reducing traffic through the router 102 and/or (iii)temporarily changing the line 306 upload speed and/or download speed.

In some embodiments, a QoS parameter associated with a connection trackis a queue requirement and step 224 comprises evaluating queue statusand performing the step of (i) dropping one or more connection tracksfrom the router when the queue status does not satisfy the first valueof the queue requirement and/or (ii) changing the value of the queuerequirement thereby reducing traffic through the router and/or (iii)adjusting the maximum upload rate and/or download rate between therouter and an Internet Service Provider.

In some embodiments, a QoS parameter associated with a connection trackis a router path requirement and step 224 comprises evaluating routerpath status of a first router path specified by the router pathrequirement and performing the step of (i) dropping one or moreconnection tracks from the router when the first router path in therouter specified by the router path requirement has insufficientbandwidth for a connection track, and/or (ii) changing a value of a QoSparameter for each of one or more connection tracks thereby reducingtraffic through the first router path specified by the router pathrequirement when the first router path has insufficient bandwidth and/or(iii) adjusting the maximum upload rate and/or download rate between therouter and an Internet Service Provider.

Step 226 In step 226, the connection track data structure 38 is removedfrom the lookup table 34 when the associated connection track has beenrouted through network switch 16 to the appropriate endpoint 104.

The present invention can be implemented as a computer program productthat comprises a computer program mechanism embedded in a computerreadable storage medium. Further, any of the methods of the presentinvention can be implemented in one or more computers or computersystems. Further still, any of the methods of the present invention canbe implemented in one or more computer program products. Someembodiments of the present invention provide a computer system or acomputer program product that encodes or has instructions for performingany or all of the methods disclosed herein. Such methods/instructionscan be stored on a CD-ROM, DVD, magnetic disk storage product, or anyother computer readable data or program storage product. Such methodscan also be embedded in permanent storage, such as ROM, one or moreprogrammable chips, or one or more application specific integratedcircuits (ASICs). Such permanent storage can be localized in a server,802.11 access point, 802.11 wireless bridge/station, repeater, router,mobile phone, or other electronic devices. Such methods encoded in thecomputer program product can also be distributed electronically, via theInternet or otherwise, by transmission of a computer data signal (inwhich the software modules are embedded) either digitally or on acarrier wave.

Some embodiments of the present invention provide a computer programproduct that contains any or all of the program modules or method stepsshown in FIGS. 1 and/or 2. These program modules can be stored on aCD-ROM, DVD, magnetic disk storage product, or any other computerreadable data or program storage product. The program modules can alsobe embedded in permanent storage, such as ROM, one or more programmablechips, or one or more application specific integrated circuits (ASICs).Such permanent storage can be localized in a server, 802.11 accesspoint, 802.11 wireless bridge/station, repeater, router, mobile phone,or other electronic devices. The software modules in the computerprogram product can also be distributed electronically, via the Internetor otherwise, by transmission of a computer data signal (in which thesoftware modules are embedded) either digitally or on a carrier wave. Itwill be appreciated that the application modules and data structuresdisclosed in FIG. 1 are for the purpose of describing aspects of thepresent disclosure. In fact, the modules and data structures disclosedin FIG. 1 can be merged into one or more modules and distributed forexecution on one or more devices that are in electronic communicationwith each other.

1. A method of routing a message, the method comprising: at a router,receiving a plurality of network layer or transport layer packets, eachpacket comprising a header and a payload and using an applicationprotocol, a subset of the packets corresponding to the message; at therouter, creating a connection track by: (i) defining the connectiontrack to be a path of the subset of packets that correspond to themessage, (ii) identifying the subset of the packets that correspond tothe message based on the packet headers and assigning the identifiedpackets to the connection track, and (iii) identifying a data type ofthe subset of packets based on the payload or application protocol ofless than all of the packets of the subset; at the router, associatingone or more quality of service (QoS) parameters with the connectiontrack based on the data type, and setting a first QoS parameter in theone or more QoS parameters to a first value in a first value range; atthe router, routing the connection track in direct accordance with theone or more QoS parameters, wherein the first QoS parameter is a routerpath requirement; at the router, routing a plurality of connectiontracks; at the router, evaluating a router path status of a first routerpath specified by the first QoS parameter; and at the router: (i)dropping one or more of the connection tracks from the router when thefirst router path in the router specified by the first QoS parameter hasinsufficient bandwidth for the connection track; and (ii) changing avalue of a second QoS parameter for one or more of the connection tracksthereby reducing traffic through the first router path specified by thefirst QoS parameter when the first router path has insufficientbandwidth; and (iii) temporarily setting a new maximum upload and/or anew maximum download rate between an Internet Service Provider and therouter.
 2. The method of claim 1, wherein the router identifies the datatype of the subset of packets based on one or more of: (i) determiningthe application protocol, and (ii) comparing the payload to one or morepredetermined data type formats.
 3. The method of claim 2, wherein therouter identifies the data type of the subset of packets based on theapplication protocol being real-time transport protocol (RTP).
 4. Themethod of claim 3, wherein the router further identifies the data typeas being real-time streaming video based the protocol being real-timestreaming transport (RTSP) protocol; or wherein the router furtheridentifies the data type as being real-time streaming audio based on theprotocol being H.323 protocol.
 5. The method of claim 2, wherein thedata type comprises encoded real-time streaming video, the methodfurther comprising: at the router, determining a characteristic of theencoded real-time streaming video; at the router, setting the first QoSparameter to a second value in the first value range when a value of thecharacteristic is within a second value range; and at the router,setting the first QoS parameter to a third value in the first valuerange when a value of the characteristic is within a third value range.6. The method of claim 5, wherein the characteristic of the encodedreal-time streaming video is a video code bitrate or the frames persecond for the encoded video.
 7. The method of claim 6, wherein one ofthe QoS parameters is a queue requirement that the router sets to saidsecond value when the real-time streaming video code bitrate is 0.5Mbit/second or less.
 8. The method of claim 6, wherein one of the QoSparameters is a queue requirement that the router sets to said secondvalue when the real-time streaming video code bitrate is 1.0 Mbit/secondor less.
 9. The method of claim 6, wherein one of the QoS parameters isa queue requirement that the router sets to said third value when thereal-time streaming video code bitrate is 0.5 Mbit/second or greater.10. The method of claim 6, wherein one of the QoS parameters is a queuerequirement that the router sets to said third value when the real-timestreaming video code bitrate is 1.0 Mbit/second or greater.
 11. Themethod of claim 2, wherein the data type is a video having apredetermined video type format.
 12. The method of claim 11, wherein thepredetermined video type format is any combination of the file formatsset forth in Table
 2. 13. The method of claim 1, further comprising, atthe router, defining a second connection track to be a second subset ofthe packets corresponding to a second message, assigning the secondsubset of the packets to the second connection track based on the packetheaders, and identifying a second data type of the second subset ofpackets based on the payload or application protocol of less than all ofthe packets of the second subset.
 14. The method of claim 1, wherein oneof the QoS parameters is a queue requirement.
 15. The method of claim14, wherein the queue requirement comprises one or more of queue buffersize, maximum allowable delay time, and a bandwidth requirement.
 16. Themethod of claim 1, wherein one of the QoS parameters is a pathdesignation.
 17. The method of claim 1, wherein one of the QoSparameters is a router processor requirement.
 18. The method of claim 1,wherein the data type comprises real-time streaming video, video ondemand, real-time streaming audio, audio data, a photographic image, anexecutable binary program, or HTML.
 19. The method of claim 18, whereinthe first QoS parameter comprises a queue requirement, a pathdesignation, or a router processor requirement.
 20. The method of claim1 wherein the plurality of network layer or transport layer packetscomprises transmission control protocol (TCP) packets, user datagramprotocol (UDP) packets, datagram congestion control packets (DCCP),stream control transmission protocol (SCTP) packets, GPRS tunnelingprotocol (GTP) packets, or Internet Control Message Protocol (ICMP)packets.
 21. The method of claim 1, wherein the router is a packetrouter.
 22. The method of claim 1, wherein the router is a flow router.23. The method of claim 1, further comprising, at the router, encodingthe subset of packets with a wrapper and storing the first QoS parameterin the wrapper.
 24. The method of claim 1, further comprising, at therouter, encoding the subset of packets with a wrapper, storing the oneor more QoS parameters in a lookup table, and storing in the wrapper apointer to the one or more QoS parameters in the lookup table.
 25. Themethod of claim 24, wherein the lookup table comprises the QoSparameters for a plurality of connection tracks in the router.
 26. Themethod of claim 25, further comprising, at the router, purging thelookup table of the QoS parameters for a first connection track in theplurality of connection tracks when the router completes routing of thefirst connection track.
 27. The method of claim 1, the method furthercomprising: at the router, routing a plurality of connection tracks; atthe router, evaluating a load of the router; at the router, performingone or more of (i) dropping one or more of the connection tracks basedupon the first value for the first QoS parameter when the router loadexceeds a threshold value; (ii) changing a first value of a QoSparameter for one or more of the connection tracks thereby reducingtraffic through the router; and (iii) temporarily setting a new maximumupload and/or a new maximum download rate between an Internet ServiceProvider and the router.
 28. The method of claim 1, wherein one of theQoS parameters is a queue requirement, the method further comprising: atthe router, routing a plurality of connection tracks; at the router,evaluating a queue status of the router; and at the router, performingone or more of: (i) dropping one or more of the connection tracks fromthe router when the queue status does not satisfy the first value of thefirst QoS parameter; (ii) changing a first value of a QoS parameter forone or more of the connection tracks thereby reducing traffic throughthe router; and (iii) temporarily setting a new maximum upload and/or anew maximum download rate between an Internet Service Provider and therouter.
 29. The method of claim 1, wherein the second QoS parameter is arouter processor requirement.
 30. The method of claim 1, wherein thesecond QoS parameter is queue buffer size, maximum allowable delay time,and/or a bandwidth requirement.
 31. The method of claim 1, the methodfurther comprising, at the router, changing a value of a plurality ofQoS parameters for the connection track thereby reducing traffic throughthe first router path specified by the first QoS parameter.
 32. Themethod of claim 1, wherein one of the QoS parameters is a routerprocessor requirement, the method further comprising: at the router,routing a plurality of connection tracks; evaluating router processoravailability; and at the router, performing one or more of: (i) droppingone or more of the connection tracks from the router when insufficientrouter processor time is available to process said connection track;(ii) changing a first value of a QoS parameter for one or more of theconnection tracks thereby reducing traffic though the router; and (iii)temporarily setting a new maximum upload and/or a new maximum downloadrate between an Internet Service Provider and the router.
 33. The methodof claim 1, wherein the router further assigns the subset of packets tothe connection track based on a TCP or UDP port identified in the packetheader of a packet of the subset.
 34. A non-transitory computer-readablemedium embedded with a computer executable program includinginstructions for: causing a router to receive a plurality of networklayer or transport layer packets, each packet comprising a header and apayload and using an application protocol, a subset of the packetscorresponding to a message; causing the router to create a connectiontrack by causing the router to: (i) define the connection track to be apath of the subset of the packets corresponding to the message, (ii)identify the subset of the packets that correspond to the message basedon the packet headers and assign the identified packets to theconnection track, and (iii) identifying a data type of the subset ofpackets based on the payload or application protocol of less than all ofthe packets of the subset; causing the router to associate one or morequality of service (QoS) parameters with the connection track based onthe data type, and to set a first QoS parameter in the one or more QoSparameters to a first value in a first value range; and causing therouter to route the connection track in direct accordance with the oneor more QoS parameters, wherein the first QoS parameter is a router pathrequirement; causing the router to route a plurality of connectiontracks; causing the router to evaluate a router path status of a firstrouter path specified by the first QoS parameter; and causing the routerto: (i) drop one or more of the connection tracks from the router whenthe first router path in the router specified by the first QoS parameterhas insufficient bandwidth for the connection track; and (ii) change avalue of a second QoS parameter for one or more of the connection tracksthereby reducing traffic through the first router path specified by thefirst QoS parameter when the first router path has insufficientbandwidth; and (iii) temporarily set a new maximum upload and/or a newmaximum download rate between an Internet Service Provider and therouter.
 35. The non-transitory computer-readable medium of claim 34,wherein the instructions for causing the router to identify the datatype of the subset of packets comprise instructions for: (i) causing therouter to identify the application protocol, or (ii) causing the routerto compare the payload to one or more predetermined data type formats.36. A router for routing data packets corresponding to a message, therouter comprising: a processor; and a memory, coupled to the processor,the memory storing instructions for execution by said processor, saidinstructions comprising instructions for: receiving a plurality ofnetwork layer or transport layer packets, each packet comprising aheader and a payload and using an application protocol, a subset of thepackets corresponding to the message; creating a connection track by:(i) defining a connection track to be a path of the subset of thepackets corresponding to the message, (ii) identifying the subset of thepackets that correspond to the message based on the packet headers andassigning the identified packets to the connection track, and (iii)identifying a data type of the subset of packets based on the payload orapplication protocol of less than all of the packets of the subset;associating one or more quality of service (QoS) parameters with theconnection track based on the data type, and setting a first QoSparameter in the one or more QoS parameters to a first value in a firstvalue range; routing the connection track in direct accordance with theone or more QoS parameters, wherein the first QoS parameter is a routerpath requirement; routing a plurality of connection tracks; evaluating arouter path status of a first router path specified by the first QoSparameter; dropping one or more of the connection tracks from the routerwhen the first router path in the router specified by the first QoSparameter has insufficient bandwidth for the connection track; changinga value of a second QoS parameter for one or more of the connectiontracks thereby reducing traffic through the first router path specifiedby the first QoS parameter when the first router path has insufficientbandwidth; and temporarily setting a new maximum upload and/or a newmaximum download rate between an Internet Service Provider and therouter.
 37. The router of claim 36, wherein the instructions foridentifying the data type of the subset of packets comprise instructionsfor: (i) identifying the application protocol, or (ii) comparing thepayload to one or more predetermined data type formats.
 38. The routerof claim 36, wherein the memory further stores a lookup table, andwherein the instructions further comprise instructions for: encoding thesubset of packets with a wrapper; storing the one or more QoS parametersfor the connection track in the lookup table; and storing a pointer tothe one or more QoS parameters for the connection track in the wrapper.39. The router of claim 38, wherein the lookup table comprises the QoSparameters for a plurality of connection tracks in the router.
 40. Therouter of claim 39, wherein the memory further comprises instructionsfor purging the lookup table of the QoS parameters for a connectiontrack when the router completes routing of the connection track.
 41. Amethod of routing a message, the method comprising: at a router,receiving a plurality of network layer or transport layer packets, eachpacket comprising a header and a payload and using an applicationprotocol, a subset of the packets corresponding to the message; at therouter, creating a connection track by: (i) defining the connectiontrack to be a path of the subset of packets that correspond to themessage, (ii) identifying the subset of the packets that correspond tothe message based on the packet headers and assigning the identifiedpackets to the connection track, and (iii) identifying a data type ofthe subset of packets based on the payload or application protocol ofless than all of the packets of the subset; at the router, associatingone or more quality of service (QoS) parameters with the connectiontrack based on the data type, and setting a first QoS parameter in theone or more QoS parameters to a first value in a first value range; atthe router, routing the connection track in direct accordance with theone or more QoS parameters; at the router, setting a second QoSparameter in the one or more QoS parameters to a second value in asecond value range based on the data type; and at the router, setting athird QoS parameter in the one or more QoS parameters to a third valuein a third value range based on the data type, wherein the first QoSparameter is a queue requirement, the second QoS parameter is a pathdesignation, and the third QoS parameter is a router processorrequirement.
 42. A non-transitory computer-readable medium embedded witha computer executable program including instructions for: causing arouter to receive a plurality of network layer or transport layerpackets, each packet comprising a header and a payload and using anapplication protocol, a subset of the packets corresponding to amessage; causing the router to create a connection track by causing therouter to: (i) define the connection track to be a path of the subset ofthe packets corresponding to the message, (ii) identify the subset ofthe packets that correspond to the message based on the packet headersand assign the identified packets to the connection track, and (iii)identifying a data type of the subset of packets based on the payload orapplication protocol of less than all of the packets of the subset;causing the router to associate one or more quality of service (QoS)parameters with the connection track based on the data type, and to seta first QoS parameter in the one or more QoS parameters to a first valuein a first value range; causing the router to route the connection trackin direct accordance with the one or more QoS parameters; causing therouter to set a second QoS parameter in the one or more QoS parametersto a second value in a second value range based on the data type; andcausing the router to set a third QoS parameter in the one or more QoSparameters to a third value in a third value range based on the datatype, wherein the first QoS parameter is a queue requirement, the secondQoS parameter is a path designation, and the third QoS parameter is arouter processor requirement.
 43. A router for routing data packetscorresponding to a message, the router comprising: a processor; and amemory, coupled to the processor, the memory storing instructions forexecution by said processor, said instructions comprising instructionsfor: receiving a plurality of network layer or transport layer packets,each packet comprising a header and a payload and using an applicationprotocol, a subset of the packets corresponding to the message; creatinga connection track by: (i) defining a connection track to be a path ofthe subset of the packets corresponding to the message, (ii) identifyingthe subset of the packets that correspond to the message based on thepacket headers and assigning the identified packets to the connectiontrack, and (iii) identifying a data type of the subset of packets basedon the payload or application protocol of less than all of the packetsof the subset; associating one or more quality of service (QoS)parameters with the connection track based on the data type, and settinga first QoS parameter in the one or more QoS parameters to a first valuein a first value range; routing the connection track in directaccordance with the one or more QoS parameters setting a second QoSparameter in the one or more QoS parameters to a second value in asecond value range based on the data type; and setting a third QoSparameter in the one or more QoS parameters to a third value in a thirdvalue range based on the data type, wherein the first QoS parameter is aqueue requirement, the second QoS parameter is a path designation, andthe third QoS parameter is a router processor requirement.